Parametrize the SecDebugLogLevel #2524
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zzacharo
requested review from
a team,
bastelfreak,
ekohl and
smortex
as code owners
|
|
Contributor
|
Re the CLA CERN IT has an agreement with Puppetlabs that we have signed the CLA. |
traylenator
suggested changes
Feb 8, 2024
zzacharo
force-pushed
the
parametrize-debug-log-level
branch
from
5b2c37a to
fc46598
Compare
traylenator
approved these changes
Feb 8, 2024
Author
|
@smortex any chance to integrate this soon-ish? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
At the moment the module hardcodes the mod_security debug level to 0 although it allows users to configure the debug log path. This PR introduces a new parameter called
debug_log_levelto be able to configure theSecDebugLogLevel.Checklist
puppet apply)